Add 'use-next-version` comment in providers that will need rc2#58390
Merged
potiuk merged 1 commit intoapache:mainfrom Nov 17, 2025
Merged
Add 'use-next-version` comment in providers that will need rc2#58390potiuk merged 1 commit intoapache:mainfrom
potiuk merged 1 commit intoapache:mainfrom
Conversation
Apprise and Slack need to use the next version of common provider and for that we want to implement automated convention of bumping the version by release manager based on comment left by contributor that the version should be bumped. This attempts to add the comment so that we can test the upgrade.
kacpermuda
approved these changes
Nov 17, 2025
Member
Author
|
Need to merge it first to test rc2s :) |
potiuk
requested review from
bbovenzi,
dstandish,
ephraimbuddy,
hussein-awala,
jason810496,
pierrejeambrun and
uranusjr
jscheffl
approved these changes
Nov 17, 2025
8 tasks
aaron-wolmutt
pushed a commit
to aaron-wolmutt/airflow
that referenced
this pull request
Nov 20, 2025
…e#58390) Apprise and Slack need to use the next version of common provider and for that we want to implement automated convention of bumping the version by release manager based on comment left by contributor that the version should be bumped. This attempts to add the comment so that we can test the upgrade.
Copilot AI
pushed a commit
to jason810496/airflow
that referenced
this pull request
Dec 5, 2025
…e#58390) Apprise and Slack need to use the next version of common provider and for that we want to implement automated convention of bumping the version by release manager based on comment left by contributor that the version should be bumped. This attempts to add the comment so that we can test the upgrade.
itayweb
pushed a commit
to itayweb/airflow
that referenced
this pull request
Dec 6, 2025
…e#58390) Apprise and Slack need to use the next version of common provider and for that we want to implement automated convention of bumping the version by release manager based on comment left by contributor that the version should be bumped. This attempts to add the comment so that we can test the upgrade.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Apprise and Slack need to use the next version of common provider and for that we want to implement automated convention of bumping the version by release manager based on comment left by contributor that the version should be bumped.
This attempts to add the comment so that we can test the upgrade.
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rstor{issue_number}.significant.rst, in airflow-core/newsfragments.